forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: enable coverage linter for functional tests #6479
Open
knst
wants to merge
6
commits into
dashpay:develop
Choose a base branch
from
knst:feat-enable-coverage
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+41
−19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
knst
force-pushed
the
feat-enable-coverage
branch
2 times, most recently
from
December 13, 2024 14:13
f56e7cb
to
e0c580e
Compare
This pull request has conflicts, please rebase. |
…oteraw We indeed doesn't have functional tests for them yet, but this linter will help to avoid adding new RPCs without tests
knst
force-pushed
the
feat-enable-coverage
branch
from
December 13, 2024 14:19
e0c580e
to
2e509b9
Compare
UdjinM6
approved these changes
Dec 14, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, utACK 2e509b9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue being fixed or feature implemented
https://github.com/dashpay/dash-issues/issues/63
What was done?
Add functional tests for
getblockheaders
Hide RPC
cleardiscouraged
(as it is used only for functional tests) and RPCgetpoolinfo
(deprecated long time ago)Add a workaround to ignore these RPCs
getmerkleblocks
,voteraw
,debug
,coinjoinsalt
at the momentEnables linter for coverage
How Has This Been Tested?
Run locally with
test/functional/test_runner.py -j20 --previous-releases --coverage --extended
Enabled in CI
Breaking Changes
N/A if hidding
cleardiscouraged
is not a breaking change.Checklist: